% !TEX TS-program = pdflatex
% !TEX encoding = UTF-8 Unicode

% This file is a template using the "beamer" package to create slides for a talk or presentation
% - Talk at a conference/colloquium.
% - Talk length is about 20min.
% - Style is ornate.

% MODIFIED by Jonathan Kew, 2008-07-06
% The header comments and encoding in this file were modified for inclusion with TeXworks.
% The content is otherwise unchanged from the original distributed with the beamer package.

\documentclass{beamer}


% Copyright 2004 by Till Tantau <tantau@users.sourceforge.net>.
%
% In principle, this file can be redistributed and/or modified under
% the terms of the GNU Public License, version 2.
%
% However, this file is supposed to be a template to be modified
% for your own needs. For this reason, if you use this file as a
% template and not specifically distribute it as part of a another
% package/program, I grant the extra permission to freely copy and
% modify this file as you see fit and even to delete this copyright
% notice. 


\mode<presentation>
{
  \usetheme{Warsaw}
  % or ...

  \setbeamercovered{transparent}
  % or whatever (possibly just delete it)
}


\usepackage[english]{babel}
% or whatever

\usepackage[utf8]{inputenc}
% or whatever

\usepackage{times}
\usepackage{hyperref}
\usepackage[T1]{fontenc}
% Or whatever. Note that the encoding and the font should match. If T1
% does not look nice, try deleting the line with the fontenc.


\title[pymongo + web.py] % (optional, use only with long paper titles)
{R codename --a tiny case study}


\author[Zhilei Ren] % (optional, use only with lots of authors)
{Zhilei Ren}
% - Give the names in the same order as the appear in the paper.
% - Use the \inst{?} command only if the authors have different
%   affiliation.

% This is only inserted into the PDF information catalog. Can be left
% out. 



% If you have a file called "university-logo-filename.xxx", where xxx
% is a graphic format that can be processed by latex or pdflatex,
% resp., then you can add a logo as follows:

% \pgfdeclareimage[height=0.5cm]{university-logo}{university-logo-filename}
% \logo{\pgfuseimage{university-logo}}



% Delete this, if you do not want the table of contents to pop up at
% the beginning of each subsection:


% If you wish to uncover everything in a step-wise fashion, uncomment
% the following command: 

%\beamerdefaultoverlayspecification{<+->}


\begin{document}

\begin{frame}
  \titlepage
\end{frame}



% Structuring a talk is a difficult task and the following structure
% may not be suitable. Here are some rules that apply for this
% solution: 

% - Exactly two or three sections (other than the summary).
% - At *most* three subsections per section.
% - Talk about 30s to 2min per frame. So there should be between about
%   15 and 30 frames, all told.

% - A conference audience is likely to know very little of what you
%   are going to talk about. So *simplify*!
% - In a 20min talk, getting the main ideas across is hard
%   enough. Leave out details, even if it means being less precise than
%   you think necessary.
% - If you omit details that are vital to the proof/implementation,
%   just say so once. Everybody will be happy with that.


\begin{frame}
    It all started from a discussion

    \scriptsize
    \url{http://www.newsmth.net/nForum/\#!article/DataScience/15193?p=1\#a0}

    \includegraphics[height=0.3 \textwidth]{post0.png}
    \includegraphics[height=0.3 \textwidth]{post.png}
\end{frame}

\begin{frame}
    \begin{block}{Codename jokes are popular in software}
        It is hard to write a simple definition of something as varied as hacking, but I think what these activities have in common is playfulness, cleverness, and exploration. Thus, hacking means exploring the limits of what is possible, in a spirit of playful cleverness. Activities that display playful cleverness have "hack value".  
        
        \flushright -- Richard Stallman
    \end{block}

    \scriptsize
    \url{https://stallman.org/articles/on-hacking.html}
\end{frame}
\begin{frame}
    \begin{block}{\TeX}


Knuth has declared that he will do no further development of \TeX{}; he will continue to fix any bugs that are reported to him (though bugs are rare). This decision was made soon after \TeX{} version 3.0 was released; at each bug-fix release the version number acquires one more digit, so that it tends to the limit $\pi$ (at the time of writing, Knuth's latest release is version 3.1415926). Knuth wants \TeX{} to be frozen at version $\pi$ when he dies; thereafter, no further changes may be made to Knuth's source. (A similar rule is applied to MetaFont; its version number tends to the limit e, and currently stands at 2.718281.) 
    \end{block}

    \scriptsize
    \url{http://www.tex.ac.uk/FAQ-TeXfuture.html}
\end{frame}

\begin{frame}
    \begin{block}{Debian}
        Releases of the Debian distribution have both traditional version numbers and codenames based on characters from the Pixar/Disney movie "Toy Story" (1995). Sid, as you may recall, was the evil neighbor kid who broke all the toys. 
    \end{block}
    \includegraphics[height=0.3 \textwidth]{debian.png}

    \scriptsize
    \url{https://wiki.debian.org/DebianReleases}
\end{frame}
\begin{frame}
    Sid

    \includegraphics[height=0.3 \textwidth]{debcode/sid.jpg}
\end{frame}
\begin{frame}
    Stretch

    \includegraphics[height=0.3 \textwidth]{debcode/stretch.png}
\end{frame}
\begin{frame}
    Jessie

    \includegraphics[height=0.3 \textwidth]{debcode/jessie.jpg}
\end{frame}
\begin{frame}
    Wheezy

    \includegraphics[height=0.3 \textwidth]{debcode/wheezy.jpg}
\end{frame}
\begin{frame}
    Squeeze

    \includegraphics[height=0.3 \textwidth]{debcode/Squeeze.jpg}
\end{frame}
\begin{frame}
    Lenny

    \includegraphics[height=0.3 \textwidth]{debcode/Lenny.jpg}
\end{frame}
\begin{frame}
    Etch

    \includegraphics[height=0.3 \textwidth]{debcode/Etch.jpg}
\end{frame}
\begin{frame}
    Sarge

    \includegraphics[height=0.3 \textwidth]{debcode/Sarge.jpg}
\end{frame}
\begin{frame}
    Woody

    \includegraphics[height=0.3 \textwidth]{debcode/Woody.jpg}
\end{frame}
\begin{frame}
    Potato

    \includegraphics[height=0.3 \textwidth]{debcode/potato.jpg}
\end{frame}
\begin{frame}
    Slink

    \includegraphics[height=0.3 \textwidth]{debcode/slink.jpg}
\end{frame}
\begin{frame}
    Ham

    \includegraphics[height=0.3 \textwidth]{debcode/hamm.jpg}
\end{frame}
\begin{frame}
    Bo

    \includegraphics[height=0.3 \textwidth]{debcode/bo.jpg}
\end{frame}
\begin{frame}
    Rex

    \includegraphics[height=0.3 \textwidth]{debcode/rex.jpg}
\end{frame}
\begin{frame}
    Buzz

    \includegraphics[height=0.3 \textwidth]{debcode/buzz.jpg}
\end{frame}
\begin{frame}
    \begin{block}{Ubuntu}
The development codename of a release takes the form "Adjective Animal". So for example: Warty Warthog (Ubuntu 4.10), Hoary Hedgehog (Ubuntu 5.04), Breezy Badger (Ubuntu 5.10), are the first three releases of Ubuntu. In general, people refer to the release using the adjective, like "warty" or "breezy". The names live on in one hidden location---the archive release name in /etc/apt/sources.list and seen on the download mirror network. 
    \end{block}
    \includegraphics[height=0.3 \textwidth]{ubuntu.jpg}

    \scriptsize
    \url{https://wiki.ubuntu.com/DevelopmentCodeNames}
\end{frame}

\begin{frame}
    \begin{block}{Android}
        At a high level, Android development happens around families of releases, which use code names ordered alphabetically after tasty treats.
    \end{block}
    \includegraphics[height=0.3 \textwidth]{android.jpg}

    \scriptsize
    \url{https://source.android.com/source/build-numbers.html}
\end{frame}
\begin{frame}
\scriptsize
\url{http://www.peanuts.com/search/}

\url{http://amureprints.com/}

\url{http://www.gocomics.com/peanuts/}

\includegraphics[width=0.5 \textwidth]{compiling.png}

\end{frame}
\end{document}


